I proposed environment-specific config files a long time ago (on Discord), but remember people not liking the idea. The question was asked: why not do it with env variables? Furthermore, because or config files are php files, you could have conditionals:

if (get(Environment::class)->isLocal()) {
    return new SQLiteConfig();
} 

return new PostgresConfig();

I'm not against per-file configs, but I also don't have a very strong opinion on the matter.

Why not support both? People preferring conditionals in a single file can do this, and those preferring adding a storage.dev.config.php file to .gitignore can do that as well

That being said, Tempest should have a "recommendation" regarding the best way to handle this, because people are going to look for the idiomatic, Tempest way

Ok two thoughts:

• I believe this PR prioritizes one over the other, but still loads all? If we allow this syntax, it shouldn't load non-matching environment config files at all.
• I think the recommendation should be:

1. Use .config.php by default
2. Use env() when possible
3. Use separate, environment specific config files when needed
4. If you need even more flexibility, do whatever you want by making your config files conditional

Yes, it loads all, so the last ones would override the previous ones. I'll update the PR for only loading .local in dev and .prod in production

And I totally agree with that recommendation 👍

Cool. Feel free to merge then when it's been changed :) Will you update the docs as well?

Sure!